BBS Toolkit

home *** CD-ROM | disk | FTP | other *** search

/ BBS Toolkit / BBS Toolkit.iso / wildcat / wmail209.zip / WM.DOC < prev next >

Wrap

Text File | 1993-03-24 | 111KB | 2,775 lines

WILDMAIL! v2.09 Echomail Processor for WILDCAT! v3.00-3.02 thru v3.6x (c) Copyright 1991, 1993 by Online Computer Resources 2036 Columbus Pkwy, Suite 405, Benicia, CA 94510 Voice: (707) 552-1122 BBS: (707) 552-0602 All Rights Reserved Revised: 02/13/93 WILDMAIL! TABLE OF CONTENTS INTRODUCTION . . . . . . . . . . . . . . . . . . . . . . . . 1 ABOUT THIS DOCUMENTATION . . . . . . . . . . . . . . . . . . 2 ACKNOWLEDGEMENTS . . . . . . . . . . . . . . . . . . . . . . 3 REGISTRATION/ORDERING INFORMATION . . . . . . . . . . . . . . 3 INSTALLATION . . . . . . . . . . . . . . . . . . . . . . . . 4 FILES INCLUDED . . . . . . . . . . . . . . . . . . . . . 4 UPGRADING WILDMAIL! . . . . . . . . . . . . . . . . . . 5 INSTALLING WILDMAIL! FOR THE FIRST TIME . . . . . . . . 6 COMMAND LINE OPTIONS . . . . . . . . . . . . . . . . . . . . 7 USAGE . . . . . . . . . . . . . . . . . . . . . . . . . 7 ? . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 TOSS . . . . . . . . . . . . . . . . . . . . . . . . . . 7 SCAN . . . . . . . . . . . . . . . . . . . . . . . . . . 8 PACK . . . . . . . . . . . . . . . . . . . . . . . . . . 8 PURGE . . . . . . . . . . . . . . . . . . . . . . . . . 8 REBUILD . . . . . . . . . . . . . . . . . . . . . . . . 9 -A . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 -N . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 -R . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 -S . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 -T . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 -Q . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 AREAS.BBS FILE . . . . . . . . . . . . . . . . . . . . . . . 11 AREAFIX . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 WM.CFG FILE . . . . . . . . . . . . . . . . . . . . . . . . . 13 GENERAL CONFIGURATION INFORMATION . . . . . . . . . . . 13 ZONE . . . . . . . . . . . . . . . . . . . . . . . 13 ADDRESS . . . . . . . . . . . . . . . . . . . . . . 13 MAILER . . . . . . . . . . . . . . . . . . . . . . 14 INBOUND . . . . . . . . . . . . . . . . . . . . . . 14 AKA . . . . . . . . . . . . . . . . . . . . . . . . 14 ADDTOSEENBY . . . . . . . . . . . . . . . . . . . . 14 MAP_ZONE . . . . . . . . . . . . . . . . . . . . . 15 DEFAULT_ZONE . . . . . . . . . . . . . . . . . . . 15 MATCH_ZONE . . . . . . . . . . . . . . . . . . . . 16 OUT_ZONE . . . . . . . . . . . . . . . . . . . . . 17 POINTBOSS . . . . . . . . . . . . . . . . . . . . . 18 POINTNET . . . . . . . . . . . . . . . . . . . . . 18 i WILDMAIL! TABLE OF CONTENTS WILDCAT . . . . . . . . . . . . . . . . . . . . . . 18 NETMAIL . . . . . . . . . . . . . . . . . . . . . . 18 MATRIXMAIL . . . . . . . . . . . . . . . . . . . . 19 OUTBOUND . . . . . . . . . . . . . . . . . . . . . 19 LOG . . . . . . . . . . . . . . . . . . . . . . . . 19 BADECHO . . . . . . . . . . . . . . . . . . . . . . 20 DUPLICATES . . . . . . . . . . . . . . . . . . . . 20 MAXMESSAGES . . . . . . . . . . . . . . . . . . . . 20 NULLMESSAGE . . . . . . . . . . . . . . . . . . . . 21 KILLSENT . . . . . . . . . . . . . . . . . . . . . 21 INTLADDRESSING . . . . . . . . . . . . . . . . . . 21 NONETMAILMESSAGE . . . . . . . . . . . . . . . . . 21 NOTIFY . . . . . . . . . . . . . . . . . . . . . . 21 PURGE . . . . . . . . . . . . . . . . . . . . . . . 22 STANDARDARCHIVE . . . . . . . . . . . . . . . . . . 22 UNPACKER . . . . . . . . . . . . . . . . . . . . . 23 PACKER . . . . . . . . . . . . . . . . . . . . . . 24 TYPEPACK . . . . . . . . . . . . . . . . . . . . . 24 SWAP<> . . . . . . . . . . . . . . . . . . . . . 25 DELETESEENBYLINES . . . . . . . . . . . . . . . . . 26 SHOWSEENBYLINES . . . . . . . . . . . . . . . . . . 26 DELETEAFTERTOSSING . . . . . . . . . . . . . . . . 26 FORWARDPACKETS . . . . . . . . . . . . . . . . . . 26 NOEMS . . . . . . . . . . . . . . . . . . . . . . . 27 LOCKCOUNT . . . . . . . . . . . . . . . . . . . . . 27 QUIETARC . . . . . . . . . . . . . . . . . . . . . 27 SEENBYCHECKING . . . . . . . . . . . . . . . . . . 28 SAMPLE DISPLAY SCREEN . . . . . . . . . . . . . . . . . . . . 29 WINDOW DEFINITIONS . . . . . . . . . . . . . . . . . . . 29 INBOUND MAIL ARCHIVES . . . . . . . . . . . . . . . 29 STATISTICS . . . . . . . . . . . . . . . . . . . . 30 MAIL PACKET QUEUE . . . . . . . . . . . . . . . . . 30 CURRENT ACTIVITY . . . . . . . . . . . . . . . . . 30 FREE MEMORY . . . . . . . . . . . . . . . . . . . . 30 ORIGIN LINES . . . . . . . . . . . . . . . . . . . . . . . . 31 HELP SCREEN . . . . . . . . . . . . . . . . . . . . . . . . . 32 EXIT ERRORLEVELS . . . . . . . . . . . . . . . . . . . . . . 33 ii WILDMAIL! TABLE OF CONTENTS WILDMAIL! LICENSING AND DISTRIBUTION AGREEMENT . . . . . . . 34 NO WARRANTY . . . . . . . . . . . . . . . . . . . . . . 36 TECHNICAL SUPPORT . . . . . . . . . . . . . . . . . . . . . . 37 APPENDIX A, LIMITS AND SIZES . . . . . . . . . . . . . . . . 38 MEMORY REQUIREMENTS . . . . . . . . . . . . . . . . . . 38 WM.CFG FILE LIMITS . . . . . . . . . . . . . . . . . . . 38 APPENDIX B, OTHER TECHNICAL NOTES . . . . . . . . . . . . . . 39 TOSSING ARCMAIL IN DATE/TIME ORDER . . . . . . . . . . 39 NODE NUMBER SYNTAX SHORTCUTS . . . . . . . . . . . . . . 39 LARGE MESSAGES . . . . . . . . . . . . . . . . . . . . . 39 NO CONTENT MESSAGES . . . . . . . . . . . . . . . . . . 39 FRONTDOOR BATCH FILES . . . . . . . . . . . . . . . . . . . . 40 ASSOCIATED BATCH FILES . . . . . . . . . . . . . . . . . 40 SYSTEM FLOW . . . . . . . . . . . . . . . . . . . . . . 41 CAT.BAT EXPLANATION . . . . . . . . . . . . . . . . . . 42 DOBBS.BAT . . . . . . . . . . . . . . . . . . . . . . . 46 EXEBBS.BAT . . . . . . . . . . . . . . . . . . . . . . . 47 iii WILDMAIL! v2.09 CHANGES BUG FIXES o Fixed the problem where WILDCAT! would crap out if a user logged on to a node while WM was running. iv WILDMAIL! v2.09 EVALUATION KEY 30 DAY EVALUATION KEY FILE WILDMAIL! utilizes a special file to activate its usage for a period of 30 days. This method allows the program to be fully utilized with all options enabled for the duration of the evaluation period. If the product hasn't been registered after the thirty days, WILDMAIL! will inform you it has expired and will simply cease to run. Since the current method of distribution prevents a "dated" key file from be included in WMAIL208.ZIP, you must dial up the support board (listed below) and create this special key file. Selecting the "Create WM.ID Key File" option from the Main Menu initiates this process and you simply enter in the required information and then follow the instructions for downloading. The WILDMAIL! support board may reached by dialing: (707) 552-0602 Only one key per person/registration number will be allowed. v WILDMAIL! v2.09 Page 1 INTRODUCTION WILDMAIL! v2.09 is an echomail processor for WILDCAT! v3.xx BBS software. WILDMAIL!, hereinafter referred to as WM, processes standard Fidonet compatible mail archives received from a front end mailer like D'Bridge, FrontDoor or BinkleyTerm. After unpacking, WM processes the .PKT files and tosses those messages directly into the corresponding WILDCAT! message conferences. It also forwards those incoming messages to nodes (up/downstream) as specified in the AREAS.BBS file. Conversely, it extracts new messages and outputs them into the .PKT format and then creates a standard Fidonet mail archive and passes that to the front end mailer to process as outbound mail. Here's a sampling of WM's capabilities: . Multi-Zone/Network support. . Able to unpack/pack most types of archive mail bundles such as ARC, PAK, LZH, ZIP, ARJ and ZOO. . Point support as both a BOSS and a POINT node. . Supports passthru conferences. . Kill duplicate messages based on a count set up in the WM.CFG file. . Supports a unique ORIGIN line per conference. . Quiet mode of operation. Turns display mode off to decrease processing time. . Status log file reporting. . Private Echomail messages. . Full screen display with statistics. WILDMAIL! v2.09 Page 2 ABOUT THIS DOCUMENTATION This document is a reference manual on how to set up and run WM. The documentation assumes that you know something about net/echomail, and is not a tutorial on how to set up and run a frontend mailer program such as FrontDoor, D'Bridge or BinkleyTerm. There is however a section on setting up the batch files for FrontDoor, but are only shown for example only. WE CAN NOT SUPPORT THE SETUP AND CONFIGURATION OF FRONTDOOR! WILDMAIL! v2.09 Page 3 ACKNOWLEDGEMENTS Thanks go to Mustang Software Inc. for creating an exceptional product in WILDCAT! v3.x. Also, thanks go to the great people who were our guinea pigs in the first versions of this program and who shared in it's development - the ALPHA/BETA testers of WILDCAT! v3.x! To them all - Thanks! Derek Koopowitz/Joe Martin Online Computer Resources 2036 Columbus Pkwy, #405 Benicia, CA 94510 Fidonet 1:161/123, 1:161/502, 1:161/503, 1:161/504 REGISTRATION/ORDERING INFORMATION International (except Australia) and USA orders are handled by us at Online Computer Resources. Australian orders are handled by Barcastle Enterprises located in Melbourne Australia. Please see the enclosed REGISTER.DOC file for full ordering information. WILDMAIL! v2.09 Page 4 INSTALLATION FILES INCLUDED Your WM installation kit is distributed in a single compressed library file containing these files: READ.ME Introductory comments and any last minute changes. WHATSNEW.nnn File(s) describing bug fixes/enhancements to WM for WM. REGISTER.DOC Registration form used when registering the product. EVALKEY.DOC How to get an evaluation key to run WM. WM.EXE WM, the executable. WM.OVR WM overlay file. WM.DOC This documentation file. WM.CFG Sample configuration file for WM. AREAS.BBS Sample file showing echomail areas and the area distribution. WMCRASH.LST Sample file showing user names that are allowed to send Netmail messages flagged as CRASH. ORIGIN.002 Sample ORIGIN.nnn file. WMRUTE.CFG Blank routing configuration file for the PACK option of WM when running under BinkleyTerm. (Not used at this time) DB-CFG.ZIP Sample configuration files for setting up D'Bridge with WM. FD-CFG.ZIP Sample configuration files for setting up FrontDoor with WM. BI-CFG.ZIP Sample configuration files for setting up BinkleyTerm with WM. WILDMAIL! v2.09 Page 5 INSTALLATION/UPGRADE UPGRADING FROM v2.00-2.07 ========================= 1. Print out the contents of your existing WM.CFG file. 2. Unzip WMAIL208.ZIP and copy WM.EXE, WM.OVR and WM.CFG files into the existing \WILDMAIL directory overwriting the previous files. 3. Using a standard ASCII editor, make the necessary changes to the new WM.CFG file to reflect your current settings from the printed out copy of your old WM.CFG file. 4. Activate/deactivate the new options as necessary in the new WM.CFG file. 5. Edit/create the WMCRASH.LST file if needed. UPGRADING WM FROM EARLIER THAN v2.00 ==================================== 1. Make a complete backup of your existing \WILDMAIL directory. Very important! Print out a copy of your existing WM.CFG file. 2. Delete all files from your existing \WILDMAIL directory EXCEPT AREAS.BBS and WM.ID if you have previously registered WM. 3. Unzip the contents of WMAIL208.ZIP into the \WILDMAIL directory allowing overwrites on everything EXCEPT your AREAS.BBS file. 4. Using a ASCII text editor, make the necessary changes to the *new* WM.CFG file from your old copy you printed out in step 2. Do NOT use your old WM.CFG file! 5. Make sure all the packer types that have been defined in your WM.CFG do in fact exist in your path. WM now checks to make sure that these compression and decompression programs physically exist prior to starting any mail processing. 6. REMOVE the old -C command line parameter from your mailers BATch file. THIS IS VERY IMPORTANT! Automatic cleanup is now performed. Refer to the *new* -N replacement option for additional information. 7. Edit/create the WMCRASH.LST file if needed. WILDMAIL! v2.09 Page 6 INSTALLATION/UPGRADE If you encounter any problems, always do your checking from the DOS prompt and NOT from a batch file. This will allow plenty of time to read whatever gets displayed to the screen. All internal error messages detected by WM will be placed in the log file that is defined in WM.CFG (normally WM.LOG) for later review. INSTALLING WM FOR THE FIRST TIME ================================ 1. Create a directory called \WILDMAIL. 2. Unzip the contents of WMAIL208.ZIP into the \WILDMAIL directory. If you've registered WM, you will need to place the WM.ID file in this directory as well. 2. Edit the WM.CFG file with any ASCII text editor to meet your specific configuration needs. Refer to the section on this file for detailed configuration information. 3. Edit the example AREAS.BBS file with any ASCII text editor and specify the WILDCAT! message conference numbers and net/node addresses which will be receiving mail. 4. Edit/create the WMCRASH.LST file if needed. 5. Edit your mailers batch file to add WM to it so that it can take care of the following tasks: . incoming mail tossing/forwarding . scheduled scanning of your echomail areas . scanning and packing mail after new messages are created on your system Various sample mailer configurations and batch files have been included with this release to aid in the setup and implementation of WM. Please refer to the appropriate xx-CFG.ZIP for your configuration needs. WILDMAIL! v2.09 Page 7 COMMAND LINE OPTIONS COMMAND LINE USAGE: WM TOSS SCAN PACK PURGE REBUILD,<# of dupes> -A<filename> -N -R<conference #>,<net/node id>,<starting msg #> -S<schedule_name> -T<conference #>,<extract count> -Q Below is a list of available command line parameters that can be used when running WM. ? This will cause WM to display a help screen that allows menu style selection of command line parameters for specific help information. Example Usage: WM ? TOSS This parameter will cause WM to toss messages into their respective message bases. Example Usage: WM TOSS This process starts off by scanning your defined BADECHO directory for any .MSG files and if there's a defined conference, tosses them into their respective conferences. Next, it proceeds to decompress the first mail archive found in the INBOUND directory and then starts the process of tossing/adding messages to their respective conferences. If the PURGE option is enabled in WM.CFG, then WM will purge the oldest message before adding a new one if the conference is at it's defined limit as specified in MAKEWILD. WILDMAIL! v2.09 Page 8 COMMAND LINE OPTIONS SCAN This is used to search for newly entered messages, then extract and forward them as defined in the AREA.BBS file. Example Usage: WM SCAN This process begins by reading the contents of AREAS.BBS for a list of conferences to process and extracts ALL messages based upon the LAST EXTRACT COUNT (see -T parameter) for that conference. Then as defined in WM.CFG with the TYPEPACK keyword, each node that has been specified to receive mail, will have it packed up in it's designated ARCHIVAL format. See TYPEPACK keyword. PACK This option is only used when BINKLEY has been selected as the Mailer type. Example Usage: WM PACK At present WM does not support it's own internal packing, bundling and routing of outbound mail. This parameter will however, call an external program called Qmail (QM.EXE with the pack option). The associated .CFG files for this program must be configured for proper operation. This program is not supplied with WM. PURGE This will maintain the allowable message count defined in MAKEWILD for each message conference configured in the AREAS.BBS file. Example Usage: WM PURGE Normally, this option would be used if you have excluded the PURGE option from the WM.CFG configuration file and could be run as a scheduled BBS event. There would be a minor savings in time to process the incoming mail, minimizing downtime of that node for processing mail. However, disk space will be taken up for those unused blank slots in the message database. WILDMAIL! v2.09 Page 9 COMMAND LINE OPTIONS REBUILD,<nnnnnn> This forces a complete rebuild of WILDDUPS.IX file located in the \WILDMAIL directory. Example Usage: WM REBUILD,5000 This will read the information stored in the WILDDUPS.DAT file and re-create a new database containing 5000 of the most current messages for duplicate checking. The <nnnnnn> option is used to override the number of duplicates you specified in the WM.CFG file. Please note the placement of the comma between REBUILD and the defined duplicates number. Also note that if the WILDDUPS.DAT file is corrupted or missing, it will be replaced by a new WILDDUPS.DAT file containing 0 messages. -A<filename> This will tell WM to use the specified file name as the AREAS.BBS file, instead of the default AREAS.BBS file. Example Usage: WM -Anewarea.bbs -N This option DISABLES a cleanup of the FrontDoor or D'Bridge outbound directory. Example Usage: WM -N WM now automatically cleans up the outbound directory prior to any tossing or extraction of messages. This option is used to override that process and leave the outbound mail archives in the outbound directory. IF THIS OPTION IS USED, IT COULD CAUSE DUPLICATES TO BE SENT OUT! PLEASE BE CAREFUL! -R<conference #>,<net/node id>,<starting msg #> This option will rescan a specified conference and extract mail for the node specified. Example Usage : WM -R14,161/502 or WM -R14,161/502,50 NOTE the placement of the "," between the <conference #>, the <net/node id> and the <starting msg #>. The first example would rescan conference number 14 and forward that mail to the address 161/502. WILDMAIL! v2.09 Page 10 COMMAND LINE OPTIONS -R<conference #>,<net/node id>,<starting msg #> - (continued) The second example would rescan conference number 14 starting at message number 50 and forward mail to the address 161/502. The starting message number is optional and if left out will force a rescan or extraction of all messages in the defined conference. Each messages ORIGINAL origin, seenby and path lines will be stripped out. USE WITH CAUTION! -S<schedule name> This will run the specified schedule name in the QM_ROUTE.CFG file. Example Usage: WM -Smysched PACK This is for BINKLEY SYSTEMS ONLY. Must be used with the PACK command. -T<conference #>,<last extracted msg #> Resets the last extract message count to the number specified for the conference. Example Usage: WM -T14,100 Note the "," comma between the <conference #> and the <last extracted msg #> as well as the conference number NEXT to the -T parameter (no spaces). The above example would reset the last extract number in conference 14 to 100. All messages numbered ABOVE 100 would then be sent during the next execution of "WM SCAN". USE WITH CAUTION! -Q QUIET Mode. WM processes the mail with minimal screen displays. Example Usage: WM TOSS -Q When this option is used, WM will display a spinning propeller on the screen to indicate activity. This option is for use when running under multitaskers like DESQview as it reduces the processing time by decreasing the resources required to maintain the WM full-screen status/activity display. WILDMAIL! v2.09 Page 11 AREAS.BBS FILE The AREAS.BBS file is a standard ASCII text file containing information used to direct WM how to process mail in and out of WILDCAT!, plus any forwarding of mail. This file can be considered the master road map for WM. The AREAS.BBS file in WILDMAIL! follows the exact same format as QuickBBS's AREAS.BBS file. First line of this file MUST contain your Origin line information followed by a # (pound sign). Typically, the origin line info is your BBS name and number. THIS MUST BE ON THE VERY FIRST LINE! Example: WILDMAIL! Support BBS - (707) 552-0602 # WM will then substitute your primary address in place of the pound sign (#). After modification, the origin line will look like: WILDMAIL! Support BBS - (707) 552-0602 (1:161/123) This will be added to every message extracted FROM your system. The TOTAL line length (including the address added by WM) must NOT exceed 65 characters. The following lines are used to create a table that identifies what WM will do for each conference configured. Each line must contain the actual WILDCAT! conference number, the EXACT conference name and the net/node address of EACH node that WM will forward new messages TO. Example: <##> <CONF> <FWD> 11 WILDCAT 1:161/503 12 ANIME 1:161/503 161/123.1 22334/2 P MENSA 1:161/504 NOTE: The titles in < >'s are shown for demonstration only! ## - The number entered here is the actual WILDCAT! conference number as defined in MAKEWILD. The letter P is used for conferences which will *NOT* be added to the message base, but rather passthru to the nodes specified in <FWD>. CONF - This MUST BE the exact conference name defined by the network you're processing mail from and not necessarily the conference description defined in MAKEWILD. If this information is misspelled, WM will toss these messages into the BADECHO directory. WILDMAIL! v2.09 Page 12 AREAS.BBS FILE FWD - These are the net/node number(s) you want to FORWARD the replies and new messages TO. Normally, this is your HUB or your downlink nodes. If WM sees an .1 attached to the node address, it will look for the POINTNET address specified in the WM.CFG configuration file. Line width is limited to 250 characters and the AREAS.BBS file can support up to 1000 conferences. Comments maybe added to the file by placing a ; (semicolon) at the beginning of each line. AREAFIX For AREAFIX users, configure AREAFIX.CTL to use a QuickBBS style format AREAS.BBS file. WILDMAIL! v2.09 Page 13 WM.CFG CONFIGURATION FILE The WM.CFG file is used to configure the operating characteristics of WM. This is a standard ASCII text file that can be edited by any number of available ASCII editors. The basic rules are as follows: . Comments are allowed by placing a ; (semi-colon) at the beginning of each line and are ignored by WM. . Keywords are defined in UPPERCASE to help distinguish them from other information. (all options are case *insensitive* to WM however) . < >'s are used to define required or optional information used with this keyword. The < >'s are NOT to be used and are shown for example only! Below is a complete list of all the available keywords and associated descriptions and sample usage formats. Each system is unique, so each option needs to be considered carefully. ZONE <number> [REQUIRED] This is your primary zone number. Example Usage: ZONE 1 Anytime you specify a network number in the WM.CFG file that doesn't include a zone (i.e. 106/111 instead of 1:106/111), WM will default the zone to the ZONE <number>. The exception to this is when you have multiple network numbers on a line and specify the zone in the previous entry. In other words: 2:10/10 10/11 12 will be interpreted as zone 2 nodes, and 10/10 10/11 12 will be interpreted as your primary ZONE nodes. ADDRESS <net/node> [REQUIRED] This is your primary network address. You would enter your net/node number here WITHOUT the zone. Example Usage: ADDRESS 161/503 WILDMAIL! v2.09 Page 14 WM.CFG CONFIGURATION FILE MAILER <mailer type> [REQUIRED] This is the front end mailer type that you run. This is used for proper handling of Netmail messages. Listed below are the three supported types. DBRIDGE - D'Bridge FRONTDOOR - FrontDoor or Seadog BINKLEY - BinkleyTerm Example Usage: MAILER FRONTDOOR INBOUND <drive:\directory path> [REQUIRED] This is the directory where all your inbound mail is placed. Example Usage: INBOUND c:\fd\file This directory MUST be the same one as defined as your INBOUND directory for your front end mailer. Normally; C:\BINKLEY\FILES for BinkleyTerm v2.40+ C:\FD\FILE for FrontDoor v1.99c or v2.02 C:\DB\FILE for D'Bridge v1.30+ AKA <zone:net/node> LIMIT: 20 [OPTIONAL] These are additional "aka" network addresses and are used to match incoming netmail messages to your alias addresses. You can define only one AKA per line, up to 20 lines are allowed. Example Usage: AKA 500:601/1234 AKA 500:390/9 ADDTOSEENBY <net/node> LIMIT: 20 [OPTIONAL] By default, WM will always add your primary address to message SEENBY's. You may specify additional nodes to be added to the SEENBY lines with this command. These additional addresses will prevent duplicate messages being sent back to you if a node downstream from you has your alias SEENBY address as their primary address to forward mail to. You can define only WILDMAIL! v2.09 Page 15 WM.CFG CONFIGURATION FILE ADDTOSEENBY - continued one ADDTOSEENBY address for each line and up to 20 lines can be defined. USE WITH CAUTION. DO NOT USE A ZONE in this statement. SEENBY's do not use zones. MAP_ZONE <net/node> <zone> MAX 10 [OPTIONAL] This option provides a measure of compatibility with mailers that do not implement fully zoned origin addresses for netmail created. This prevents WM from "assuming" a zone origin for netmail from this system, and allows for proper return addressing if mail is sent from this systems across-network or across-zone. Up to 10 MAP_ZONE statements, with one address/zone association per line, may be entered. Example Usage: MAP_ZONE 260/435 1 The above statement would ensure all incoming netmail from 260/435 will be assigned origin zone 1. Without MAP_ZONE in effect, WM will assume 260/435 to be a valid address in whatever zone the netmail is destined for. If for example, a user on 260/435 sent mail to your AKA of 100:910/3, WM would assume the origin address to be 100:260/435, completely invalidating the origin address. Adding a MAP_ZONE entry as shown above would ensure the origin address always stays as 1:260/435, regardless of the destination address. DEFAULT_ZONE <DEST> or <MYCFG> [OPTIONAL] DEFAULT_ZONE is overridden by options of the MATCH_ZONE below. Example Usage: DEFAULT_ZONE MYCFG It only applies where no MATCH_ZONE statement exists or where no MATCH_ZONE rules apply. ie., mail to a destination zone is not listed in a MATCH_ZONE statement. DEST - Set origin zone to destination zone. MYCFG - Set origin zone to default zone as defined with the ZONE keyword in the WM.CFG file. WILDMAIL! v2.09 Page 16 WM.CFG CONFIGURATION FILE MATCH_ZONE <inzone> <outzone1 outzone2... outzone10> MAX 10 [OPTIONAL] <inzone> - Zone assigned to non ^INTL mail. <outzoneNN> - Destination zones to match with <inzone>. If destination zone is in the list, then the origin zone is set to <inzone>. MATCH_ZONE is used to match up an outbound zone with a zone to be used as the origin. ie. - If the outbound mail is sent to one 1, 2, 3, 4, 5 or 6 then the origin zone is set to a 1, and if the destination zone is 100, or 410, then the origin zone is set to 100. This option is meant to provide a measure of safety for the system that acts as a network hub in more than one network. DEFAULT_ZONE, together with MATCH_ZONE, allow for the hub SysOp to ensure as well as possible, that all netmail forwarded through his or her system carries a complete origin address, including zone. DEFAULT_ZONE and MATCH_ZONE act to provide rules by which WM may assign a zone origin to netmail which carries none. DEFAULT_ZONE is overridden by specific statements made in MATCH_ZONE as per the following example: Example Usage: DEFAULT_ZONE DEST MATCH_ZONE 1 1 2 3 4 5 6 MATCH_ZONE 100 100 410 In the above example, the general rule as specified in DEFAULT_ZONE would be to assign the origin zone of forwarded netmail to be the same as the destination zone. Therefore, if mail from 260/435 were destined to 2:100/1, WM would assign zone 2 as the origin zone for 260/435. Of course, this may not always be desirable, as many networks carry multiple zones. This is where MATCH_ZONE comes in to play. The above MATCH_ZONE example overrides the DEFAULT_ZONE rules, specifying that all unzoned mail for zones 1, 2, 3, 4, 5, and 6 will be assigned to zone 1. This would result in mail from 260/435 to 2:100/1 being set to an origin address of 1:260/435. Note that DEFAULT_ZONE rules only take effect if no specific rules are entered in the MATCH_ZONE statement for the destination zone in question. Also, an alternate option for DEFAULT_ZONE is the MYCFG keyword rather than the DEST keyword. When MYCFG is used, WM is instructed to assign the zone coded in the ZONE statement for WM.CFG, rather than matching the destination zone. Up to 10 MATCH_ZONE statements may be entered in the WM.CFG file. WILDMAIL! v2.09 Page 17 WM.CFG CONFIGURATION FILE MATCH_ZONE - continued IMPORTANT NOTE! Neither DEFAULT_ZONE or MATCH_ZONE will alter an origin address for netmail if that address already carries a zone identifier. They will only add a zone where it doesn't already exist. OUT_ZONE <myakaaddr> <destzone1 destzone2... destzone10> MAX 10 [OPTIONAL] <myakaaddr> - Fully qualified zone:/net/node AKA address of my system. <destzoneNN> - Destination zones to apply the <myakaaddr> to. OUT_ZONE is used to match up an outbound zone with an AKA address to be used as the origin of the netmail message. For example, if the outbound zone is 99, then the AKA address of 99:250/1 will be used on the outbound netmail message as the origin, and if the outbound zone is a 1, 2, 3, 4, 5 or 6, the origin address will be 1:161/55520. OUT_ZONE overcomes Wildcat's inability to allow for multiple AKA's to be used for netmail (it presently supports only one origin address). Using the OUT_ZONE statement, the SysOp can have WM select the origin address for all locally created netmail, based upon the destination zone (network) the mail is intended for. Let's say, for example, one particular system carries addresses in 4 networks: 1:260/450 in FIDOnet 26:1607/100 in SIGnet 69:2601/90 in KINKnet 100:910/3 in MAGnet Using the OUT_ZONE parameter, the SysOp may "pick and choose" the conditions under which each address may be used. The following set of OUT_ZONE parameters would assure a proper origin address for all mail sent in these networks: Example Usage: OUT_ZONE 1:260/450 1 2 3 4 5 6 OUT_ZONE 26:1607/100 24 25 26 27 28 29 34 OUT_ZONE 69:2601/90 69 169 OUT_ZONE 100:910/3 100 410 610 710 Any zone destination(s) not covered in the above will result in the origin address of locally created netmail being equal to the ZONE and ADDRESS values specified in WM.CFG. Up to 10 OUT_ZONE lines may be entered in the WM.CFG file. WILDMAIL! v2.09 Page 18 WM.CFG CONFIGURATION FILE POINTBOSS <net/node> [OPTIONAL] This is used if you are operating as a point. The <net/node> is the address of your BOSS or host node. Example Usage: POINTBOSS 161/503 Do NOT include a zone number with this address. POINTNET <network number> [OPTIONAL] POINTNET is the network number of your point network. Example Usage: POINTNET 22315 If you are a host running points, then you need to make sure that this <network number> is correct. All outbound mail to your points will have their mail addressed to them using the POINTNET number defined. This number MUST be less than 32,769. WILDCAT <drive:\directory> [REQUIRED] This tells WM where your MAKEWILD.DAT and CONFDESC.DAT files are located. Example Usage: WILDCAT c:\wc30 This is commonly called the WILDCAT! home directory. NETMAIL <conference number> [REQUIRED] This is the WILDCAT! conference number of the netmail message area defined in MAKEWILD. Example Usage: NETMAIL 11 Make sure this conference is defined in MAKEWILD as a Netmail type conference. Conference numbers are numbered starting from 0 (zero). Don't use 0 as the netmail conference as WILDCAT! could possibly use this conference for [C]omments to the SysOp. DO NOT define your netmail conference in the AREAS.BBS file! WILDMAIL! v2.09 Page 19 WM.CFG CONFIGURATION FILE MATRIXMAIL <drive:\directory> [REQUIRED] This is the path to the netmail message directory. This MUST be the same <drive:\directory> as defined by your frontend mailer. Example Usage: MATRIXMAIL c:\fd\netmail WM will create netmail messages for all outbound mail, and it needs to know where to put these so your frontend mailer can process them. OUTBOUND <drive:\directory> [REQUIRED] This is where all newly created outbound mail archives will be placed. This is the SAME directory defined as outbound for your front end mailer EXCEPT FOR D'BRIDGE SYSTEMS!!!. Example Usage: OUTBOUND c:\fd\packet For D'Bridge systems, make sure that the outbound path is NOT known to D'Bridge. If the path is set to the same as D'Bridges, then D'Bridge will delete the file(s) because it won't have a corresponding QUEUE entry. WM will create a netmail message telling D'Bridge and FrontDoor that it has a file attach located in THIS directory. When D'Bridge and FrontDoor do a rescan, it will pick up this mail archive(s) and then add it to it's outbound queue. FOR BINKLEY SYSTEMS, DO NOT USE A FILE NAME EXTENSION FOR YOUR OUTBOUND AREA. WM WILL AUTOMATICALLY PUT IT IN FOR YOUR PARTICULAR ZONE. LOG <filename> [OPTIONAL] WM will keep a detailed log of what it's doing at any one point in time. Normal DOS conventions are required when defining the log file name. Example Usage: LOG wm.log The default name for the log file is WM.LOG. WILDMAIL! v2.09 Page 20 WM.CFG CONFIGURATION FILE BADECHO <drive:\directory> [REQUIRED] Where to put messages that do not have a corresponding AREAS.BBS entry. All .PKT files that contain messages that come in without having a physical conference to be placed into are tossed to this directory. Example Usage: BADECHO c:\fd\badecho These messages will be stored in the .MSG format. Typical paths are: C:\db\badecho - D'Bridge v1.30+ C:\binkley\badecho - Binkley v2.40+ C:\fd\badecho - FrontDoor v1.99c or v2.02 DUPLICATES <number> [REQUIRED] This is the number of messages to maintain for proper duplicate checking. For large hub sites, we suggest at least 3-5 DAYS worth of messages. In other words, if you typically receive 5,500 messages a day, you would use anywhere from 16500 to 27500. (3 x 5,500 = 16,500) A VALUE OF 0 INDICATES YOU WISH TO TURN DUPLICATE CHECKING OFF. Example Usage: DUPLICATES 16500 The database file this information is stored in is called WILDDUPS.DAT and contains duplicate information for *all* conferences including passthru's and is located in the \WILDMAIL directory. Please note, the larger you set this number, the larger the file size will be. MAXMESSAGES <number> [OPTIONAL] This is the maximum number of messages that will be in each .PKT file created. Example Usage: MAXMESSAGES 200 When this limit is reached, WM will create a new .PKT file for the node. Typically, 200-300 values are appropriate. If this option is not used, a default value of 300 messages is used for the .PKT size. WILDMAIL! v2.09 Page 21 WM.CFG CONFIGURATION FILE NULLMESSAGE [OPTIONAL] Delete incoming messages that have no text in the message body. Typically these are netmail file attach messages upon receipt of a mail archive. KILLSENT [OPTIONAL] All outbound netmail will be flagged as KILL/SENT if this option is enabled (uncommented). The default setting is to NOT kill the message, but flag it as being sent. INTLADDRESSING [OPTIONAL] If this option is used then all outbound netmail will have the INTL kludge line in the body of the message even if it is being sent to the same zone. The default setting is to have the INTL kludge line on ONLY those messages being sent to other zones. NONETMAILMESSAGE [OPTIONAL] When a netmail message is received, WM by default creates a netmail message (.MSG format) in the defined MATRIXMAIL directory and a netmail message in the WILDCAT! netmail conference. By enabling this option, a netmail message will ONLY be created and placed in the WILDCAT! netmail conference. No .MSG will be created if this option is used avoiding having two sets of the same netmail message. NOTE: If you run AREAFIX, then do not use this option. NOTIFY [OPTIONAL] This will scan your WILDCAT! user file to see if the 'TO:' person exists on the incoming message, and if so, it will flag the users record that there is mail waiting in the particular conference. This option will add a slight amount of processing time to the mail tossing. This also checks users Alias names if the primary user record is not found. WILDMAIL! v2.09 Page 22 WM.CFG CONFIGURATION FILE PURGE [OPTIONAL] WM will maintain the message base sizes as specified in the conference configuration. With this option enabled, WM will purge the oldest message to make room for the one about to be added if the number of messages in that conference was at it's defined limit. This is a "one for one" message purge/toss. With this option disabled, messages will be added to the message bases without maintaining the limits as defined in MAKEWILD. This will cause the database file sizes to continue to grow. You must then use the command line parameter PURGE when executing WM to properly maintain the message levels. The primary disadvantage of this, is if the PURGE option is disabled and the conference is at it limit of 750 and WM tosses 200 new messages, the database size grows to 950 messages. Then when WM is run using the PURGE option, it will purge the 200 oldest messages in the conference leaving 200 blank slots. The only way to effectively reduce the message base back down to it's true size, is to run WCREPAIR. Care must be taken when NOT using this option, otherwise you'll end up wasting a significant amount of disk space. STANDARDARCHIVE [OPTIONAL] This tells WM to use the standard archiving naming scheme of MO, TU, WE etc. for all outbound mail files. If this option is not specified, then all outbound mail archives will have the file extension of MO0. All new mail will then be added to that existing archive file without creating a new outbound archive/filename. WILDMAIL! v2.09 Page 23 WM.CFG CONFIGURATION FILE UNPACKER <constant> <command/arguments...> [REQUIRED] Here you define a specific decompression utility along with command line parameters to a CONSTANT name. This can contain any decompression method you choose for a CONSTANT, but try and keep the name consistent with the decompression method used. This command is used when decompressing mail archives from nodes specified by the TYPEPACK keyword. Typical definition of UNPACKER keyword: Keyword Constant Command/Arguments --------- ----------- ---------------------- UNPACKER ARCPACKER pkunpak.exe @a UNPACKER LZHPACKER lharc.exe x @a UNPACKER PAKPACKER pak.exe e @a UNPACKER ZIPPACKER pkunzip.exe -x @a UNPACKER ZOOPACKER zoo.exe xO @a UNPACKER ARJPACKER arj.exe e -n @a When defining the actual decompression program name, the full filename INCLUDING EXTENSION MUST BE SPECIFIED! Notice the "@a" symbol in the command arguments. This tells WM where to insert the archive name when invoking the decompression utility. For example, when decompressing a mail archive called 0000017B.MO0 that's located in the inbound directory called C:\DB\FILE, and the UNPACKER is defined as ZIPPACKER, the actual command that WM would execute would look like this: PKUNZIP.EXE -x C:\DB\FILE\0000017B.MO0 *.PKT For any additional command line arguments specific to each decompression utility, refer to it's supporting documentation for information. WILDMAIL! v2.09 Page 24 WM.CFG CONFIGURATION FILE PACKER <constant> <command/arguments> [REQUIRED] This is where you specify the compression utility along with command line parameters for a CONSTANT name. This is the opposite half of the UNPACKER keyword. This keyword is used when compressing mail archives for nodes specified by the TYPEPACK keyword. Typical definition of PACKER keyword: Keyword Constant Command/Arguments ------- --------- ----------------- PACKER ARCPACKER pkpak.exe PACKER LZHPACKER lharc.exe a /m PACKER PAKPACKER pak.exe a PACKER ZOOPACKER zoo.exe -add PACKER ZIPPACKER pkzip.exe -a PACKER ARJPACKER arj.exe a -e When defining the actual compression program, the full file name INCLUDING EXTENSION MUST BE SPECIFIED! DO NOT COMMENT OUT ARCPACKER!!!! THIS IS YOUR DEFAULT PACKER. WARNING!!!!! IF YOU CHANGE THE PACKER FOR A GIVEN NODE, YOU MUST MANUALLY UNPACK AND REPACK ANY BUNDLES THAT ALREADY EXIST IN YOUR OUTBOUND AREA FOR THAT NODE. FOR EXAMPLE, IF YOU HAVE A ZOO-CREATED BUNDLE AND SWITCH TO LHARC, THE FIRST ATTEMPT TO ADD MAIL TO THE ZOO BUNDLE WILL ABORT. TYPEPACK <constant> <nodes...> LIMIT: 3 lines per type [REQUIRED] This command is used to define what compression format each Net/Node number(s) should receive. In other words, if you have 161/123 defined in your AREAS.BBS to forward mail to, you should use the TYPEPACK keyword to define the compression method CONSTANT for THAT node number. Typical definition of TYPEPACK keyword: Keyword Constant Node Addresses -------- -------- -------------------------- TYPEPACK ZIPPACKER 161/502 503 123 2:440/7 11 WILDMAIL! v2.09 Page 25 WM.CFG CONFIGURATION FILE TYPEPACK - (continued) Typically, the definition would read like this. The nodes listed in the example would use 'pkzip.exe -a' command to compress the OUTBOUND mail (aka, PACKER keyword). Multiple nodes can be listed for each TYPEPACK keyword on each line and up to 3 lines for each CONSTANT. A point of interest when defining the nodes, in the previous example it shows 2 node addresses without network numbers. Throughout the WM.CFG file you can stack node numbers behind a specific net/node address as long as the stacked nodes have the exact same net address. In other words, the addresses: 161/502 503 123 are the same as: 161/502 161/503 161/123 This method is provided as a convenience and since both perform exactly the same, it's implementation either way is a personal preference. SWAP<swaplocation> [OPTIONAL] WM will remove part of itself from memory when performing the packing and unpacking processes and then return after the process is complete. This option is used to define which method of swapping is desired. Example Usage: SWAPEMS or SWAPDISK DISK - Swap to disk. This will create a SWAP file in the \WILDMAIL directory. EMS - Swap to EMS, if it's available. If EMS is not available and this option is selected, WM will automatically swap to disk. SWAPEMS is the recommended option. If EMS is detected, WM will automatically load its overlay file, WM.OVR there taking up approximately 125K. When actually swapping out, 385K or so memory is required. So approximately 515K of total EMS memory would be required for both the overlay file and the swap file. WILDMAIL! v2.09 Page 26 WM.CFG CONFIGURATION FILE DELETESEENBYLINES [OPTIONAL] WM will normally leave the SEENBY lines attached to the message when it's tossed into WILDCAT! These are normally hidden from view, so the caller will never know that they even exist. However, they do take up space, and by using this option, the SEENBY lines will automatically be stripped prior to being added to the message base. Sometimes, the SEENBY lines can take up to 2x the space that the actual message does. This option CANNOT be used with SHOWSEENBYLINES. Either one can be selected, but not both. SHOWSEENBYLINES [OPTIONAL] WM will normally hide the SEENBY lines so that the caller will not see them. However, it may become useful to see the SEENBY lines if there is a problem and the SysOp would like to see what systems have already seen the message. For aesthetics, this option should be left commented out so that the caller will never see the SEENBY lines. This option CANNOT be used with DELETESEENBYLINES. Either one can be selected, but not both. DELETEAFTERTOSSING [OPTIONAL] If this option is specified, then the incoming mail archive is deleted after all the .PKT files have been tossed. If this option is not used, then the mail archive is deleted right after it has been decompressed. Do not use this option if you are running low on disk space. FORWARDPACKETS [OPTIONAL] If this option is specified, then, if the incoming .PKT is not addressed to your primary address and AKA's, will be forwarded to the appropriate address. USE WITH CAUTION! If this option is not used, then, if the incoming .PKT file doesn't match your primary address or AKA's, then it is renamed to a .BAD file. WILDMAIL! v2.09 Page 27 WM.CFG CONFIGURATION FILE NOEMS [OPTIONAL] WM will normally take advantage of as much EMS memory is available to it when it runs. Two types of EMS usage are available when using WM. 1. EMS for increasing database accesses when processing mail. 2. EMS for swapping the program code out when compressing or uncompressing mail archives. The NOEMS option allows you to disable EMS usage for database accesses only. The primary purpose of this option is to prevent memory contention problems on peer-to-peer LAN's. For EMS usage controlling program swapping, please refer to the SWAPEMS/SWAPDISK option. LOCKCOUNT <number of messages> [OPTIONAL] This option determines how long the message base is locked when tossing messages into a conference. Allowable numbers can range from 0 thru 30 with a default value of 1. With a value of 1, this means the message conference being tossed into (at that point in time) will be locked and then unlocked for every new message added to the database. A value of 0 tells WM to keep the database locked until the conference being tossed into changes or the maximum 30 message limit has been reached. A value of 5 indicates the database will be locked for the next 5 messages (if they were all to go into the same conference database). The maximum value allowed is 30 so the database will only remained locked for a maximum of 30 messages and then unlocked so that other programs trying to access the conference will be allowed to do so. Caution must be exercised when using this option especially on slower PC's because in a multi-line environment, WILDCAT! will attempt to save information to a database for a period of 60 seconds before a fatal error will occur. This process is indicated by the "Lock Retry ##" being displayed in the upper RH corner of the screen. The slower the PC, the longer it can take to save messages and thereby possibly exceeding WILDCAT!'s 60 second limit. WILDMAIL! v2.09 Page 28 WM.CFG CONFIGURATION FILE LOCKCOUNT [OPTIONAL] - continued On faster machines, a value of 0 is normally sufficient, but this is on a case by case basis and warrants close monitoring to ensure time limits on locking the database files aren't exceeded. If a fatal error does occur, it indicates the number specified (in this case, a 0) should be raised to a higher value (maybe 15 or so) and executed/monitored again. Remember the higher the number, the longer the database can be locked. Please note that a value of 0 is equal to setting the LOCKCOUNT to 30. If the value specified was greater than 1, then lowering this number would reduce the likelihood of errors. It should be pointed out that WILDCAT!'s "Lock Retry ##" displayed in the upper RH corner of the screen on a node (or task in DESQview) is a simple indication that a database is locked by another node, another utility or WM while this node is attempting to save information to the same file. This is not an error and occurs from time to time in a multi-line environment. QUIETARC [OPTIONAL] This option will redirect the screen output from the compression programs to NULL thereby cleaning up the display. WM will then display information about the process in a cleanly organized manner. The default is to display everything to the screen causing various information about the compression process to scroll up the screen. For those that use LHARC/LZH as their PACKER type, bear in mind that these programs don't allow redirection and unfortunately will be displayed regardless of the setting here. SEENBYCHECKING [OPTIONAL] This option enables SEEN-BY line checking. If WM finds a message that does not have SEEN-BY lines, it tosses the message to the BAD MESSAGES directory. This option does not check for the existence of PATH lines in a message. That restriction has been removed. WILDMAIL! v2.09 Page 29 SAMPLE DISPLAY SCREEN With the v2.00 release of WILDMAIL!, a new full screen display has been added. This screen contains statistical information about the current mail processing session and a current activity window. NOTE: If you are running under DESQview, to reduce the processing time, you may want to use the -Q (Quiet mode) command line parameter. This will display only a spinning propeller to indicate activity. For further information on this option, refer to the section on command line options. Shown below is a sample screen without the -Q parameter. ┌──────────────────────────────────────────────────────────────────────────────┐ │ WILDMAIL! v2.09 Mail Processor for WILDCAT! v3.+ Reg.# 90-0002 │ └──────────────────────────────────────────────────────────────────────────────┘ ╒══ InBound Mail Archives ══╕╒════ Statistics ════╕╒════ Mail Packet Queue ════╕ │ 0000017B.MO0 1,141,621 ││ Current: 15:11:50 ││ 52361289.PKT (200) Done │ │ 0000017B.MO1 348,910 ││ Start : 14:26:37 ││ 52361290.PKT (200) Done │ │ 0000FC94.TU0 11,947 ││ Elapsed: 00:45:13 ││ 52361291.PKT (200) Done │ │ ││ Tossed : 3,498 ││ 52361292.PKT (200) Done │ │ ││ Extract: 172 ││ 52361293.PKT (275) Done │ │ ││ Forward: 165 ││ 52361294.PKT (120) Done │ │ ││ Bad Msg: 0 ││ 52361295.PKT In Process │ ╘═══════════════════════════╛╘════════════════════╛╘═══════════════════════════╛ ╒══════════════════════════════ Current Activity ══════════════════════════════╕ │ Reading the WILDMAIL! CONFIGURATION file, and checking it... just a second! │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ ╘═══════════════════════════════════════════════════════════ Free Memory: 154k ╛ 02/13/92 (c) Online Computer Resources 1991, 1993 Concord, CA (707) 552-1122 WINDOW DEFINITIONS InBound Mail Archives This window displays all mail archives found in the INBOUND files area that are in queue waiting to be processed. To the right is the archives file size prior to unpacking. WILDMAIL! v2.09 Page 30 SAMPLE DISPLAY SCREEN Statistics This is a quick stats type window that gives you information about the current mail processing session. Mail Packet Queue WM only unpacks one mail archive at a time, so the archive that is currently being processed will have the contents displayed in this window. After a .PKT file is finished being processed, the number of messages contained within that file will be displayed to the immediate right of the filename enclosed in parentheses. Current Activity This is the main processing window. All the information about what conference mail is being extracted from, tossed into and forwarded to is displayed here. Additional system related information like checking configuration and cleaning outbound directories and so on will show up here as well. Free Memory This is the amount of free memory after WM has been loaded. This only displays BASE memory, and not available EMS type memory. WILDMAIL! v2.09 Page 31 ORIGIN LINES ORIGIN LINES WM supports two possible sources for origin lines. The default is obtained from the very first line of the AREAS.BBS file. The second is by the creation of a one line text file called ORIGIN.nnn (where nnn equals conference number defined in MAKEWILD). This file must exist in the same subdirectory as that conferences MSGnnn.DAT/IX files. (Very important!) The ORIGIN.nnn file is a standard ASCII text file with the origin line you wish to use for the <nnn> conference. For conference number 14, the filename would be ORIGIN.014. Please note the inclusion of the leading zero. The file extension must be a full 3 characters long. You can have multiple ORIGIN.nnn files if desired but only one allowed per conference (number). This file contains only one line of text not to exceed a total of 60 characters. You MUST place your (zone:net/node) address enclosed in parentheses at the end of the line. Below is a sample origin line. The Power Station BBS 9 nodes! (100:910/18) Note this is very similar to the first line of your AREAS.BBS file, except it's missing the # (pound sign). When WM extracts messages, it will look to see if there is a corresponding ORIGIN.nnn file for each conference it extracts from. If found, it will use that files origin line when adding origins to the messages extracted from that conference. If there is no corresponding ORIGIN.nnn file, it will use the default found in the AREAS.BBS file. This option is very useful if you have echoes that are in other networks (not your primary network), and you want to have a different address show up in the origin line. You could also use this to specify a unique origin line for each conference that you have. WILDMAIL! v2.09 Page 32 HELP SCREEN If WM is run from the command line with incorrect or missing parameters, it will display a help screen allowing you the option of selecting a specific parameter to obtain help on. Shown below is a sample screen. WILDMAIL! v2.09 - Mail Processor for WILDCAT! 3.x Select the option you would like more information on : A] TOSS B] SCAN C] PACK D] REBUILD,<# of dupes> E] PURGE F] -A<filename> G] -N H] -Q I] -R<conference #>,<net/node id>,<starting msg #> J] -S<schedule name> K] -T<conference #>,<extract count> ?] General command line information. Press [ENTER] to exit, or enter an item to view : By selecting the corresponding option letter, you will be shown information on the selected command. Selecting option 'H' presents the following information. COMMAND : -Q Example Usage : "WM -Q" QUIET MODE. WILDMAIL! processes the mail with no screen displays. Speeds up processing time by decreasing the resources required to maintain the WILDMAIL! full-screen activity display. Press [ENTER] to continue... After an option letter has been chosen and the information displayed, pressing [ENTER] will return you to the main help screen. From here you can continue to select more options for additional help or exit the help mode by pressing [ENTER] and you will be returned to the DOS prompt. WILDMAIL! v2.09 Page 33 ERRORLEVELS Upon exit, WM will register a DOS error level. If there are any errors encountered when exiting WM, these will be noted in the log file defined in WM.CFG. Normally, this is WM.LOG. 0 . . . Completed successfully 1 . . . WM.CFG or AREAS.BBS error 2 . . . Not enough disk space to toss mail 9 . . . Fatal error WILDMAIL! v2.09 Page 34 WM LICENSING AND DISTRIBUTION AGREEMENT Copyright (C) 1991, 1993 by Online Computer Resources. ALL RIGHTS RESERVED. COMMERCIAL DISTRIBUTION AND/OR USE PROHIBITED WITHOUT WRITTEN PERMISSION FROM Online Computer Resources. Non-Commercial distribution and/or use is permitted under the following terms: 1) You may copy and distribute copies of WM executable code as you receive it, in any medium, provided that you do so in a lawful, friendly manner and that you conspicuously and appropriately publish on each copy of each file that is a part of the distribution package a valid copyright notice: "Copyright (C) 1991, 1993 by Online Computer Resources. Any copies that you distribute must be distributed free of charge to the recipient of the copy. WM may not be sold and you may not rent or lease it to any other person." 2) You must keep this License Agreement intact and give any other recipients of the WM program a copy of this License Agreement along with the program. 3) You must distribute WM in unmodified form. You may not add an advertisement for your Bulletin Board System, User Group, or anything else either as a file in the distribution packet or as a header in any archive. You may not add, modify or delete any of the files in the WM distribution archive. 4) WM must be distributed for free. You may not charge a distribution fee for the physical act of transferring a copy of this program. You may not place this program in any file area of a Bulletin Board System where a fee is required for download. 5) You may not modify your copy or copies of WM or any portion of it and you can not copy and distribute any modifications. WM is distributed in ZIP format and you may not distribute it in any other form. 6) You may not copy, sublicense, distribute or transfer WM except as expressly provided under this License Agreement. Any attempt otherwise to copy, sublicense, distribute or transfer WM is void and your rights to use the program under this License agreement shall be automatically terminated. WILDMAIL! v2.09 Page 35 WM LICENSING AND DISTRIBUTION AGREEMENT 7) You may not incorporate parts of WM into other programs without the written permission of Online Computer Resources. Permission may or may not be granted based upon a determination of what your intended use is. 8) For the purposes of this document, "COMMERCIAL USE" is defined as concurrent operation of the software on three or more computers or data lines owned by the same for-profit organization. Any organization may operate this software under the terms of this Non-Commercial Agreement if operation is limited to two or less computers or data lines. 9) You may use the software only after understanding and agreeing upon the above terms. WILDMAIL! v2.09 Page 36 WM LICENSING AND DISTRIBUTION AGREEMENT NO WARRANTY =========== WILDMAIL! v2.09 IS DISTRIBUTED AS AN EVALUATION COPY ONLY! THIS PROGRAM REQUIRES THE USE OF A SPECIAL 30 EVALUATION KEY OBTAINABLE FROM THE WM SUPPORT BBS AT (707) 552-0602. IF, AT THE END OF THE 30 DAY PERIOD, YOU HAVE NOT REGISTERED THE PRODUCT, WM WILL SIMPLY CEASE TO RUN. REACTIVATION REQUIRES THE PLACEMENT OF THE REGISTERED KEY FILE IN THE WM DIRECTORY. THIS PROGRAM IS GUARANTEED TO DO ABSOLUTELY NOTHING EXCEPT TAKE UP DISK SPACE. USE IT AT YOUR OWN RISK. NEITHER ONLINE COMPUTER RESOURCES NOR ANY OTHER PERSON INVOLVED IN IT'S DISTRIBUTION IS RESPONSIBLE IN ANY WAY, FOR ANY DAMAGES RESULTING FROM ITS USE OR MISUSE, DIRECTLY OR INDIRECTLY. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF WM IS ENTIRELY WITH YOU. SHOULD WM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR OTHER DAMAGES TO YOUR EQUIPMENT, SOFTWARE, OR OTHER PROPERTY. ONLINE COMPUTER RESOURCES IS NOT RESPONSIBLE TO YOU FOR DAMAGES, INCLUDING BUT NOT LIMITED TO, ANY LOST PROFITS, LOST MONIES, OR OTHER SPECIAL, GENERAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS) OR ANY OTHER LOSS EVEN IF YOU HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES, OR FOR ANY CLAIM BY ANY OTHER PARTY. WILDMAIL! v2.09 Page 37 TECHNICAL SUPPORT TECHNICAL SUPPORT You may contact Online Computer Resources at 1:161/123, 1:161/502, 1:161/503 or 1:161/504 via netmail or by logging on to the BBS for technical support. We can also be reached in the WILDCAT! conference on Fidonet. Business hours are 9am-6pm M-F and 10am-5pm Saturdays PST and our VOICE number is (707) 552-1122. When calling for support, be prepared to have a copy of your AREAS.BBS and WM.CFG files available. These MUST be the ones you're CURRENTLY using. For even faster support, zip up those two files into a unique file name and send them to our support board at: (707) 552-0602 If your files are already on our system before you call, we will be able to immediately look at your present configuration and offer any needed assistance much faster and more effectively. 30 DAY EVALUATION COPY WILDMAIL! v2.09 is a fully functional, full featured mail processor for WILDCAT! v3.xx. This program is not disabled in any way but does require the use of a special 30 day evaluation key. This key is obtainable by dialing the WM support BBS at the number listed above. This temporary key will allow WILDMAIL! to run FOR 30 DAYS without registration, after which, the program will simply cease to run. This should be sufficient time to properly evaluate the program for fitness prior to its actual registration. After you register the program, you will receive the WM.ID file and then by placing it in the \WILDMAIL directory, it will reactivate the program for normal use. WILDMAIL! v2.09 Page 38 APPENDIX A APPENDIX A, LIMITS AND SIZES MEMORY REQUIREMENTS Memory for WM . . . . . . . . . . . . . . . . . . . . 385k WM.CFG FILE LIMITS AKA . . . . . . . . . . . . . . . . . . . . . . . 20 lines ADDTOSEENBY . . . . . . . . . . . . . . . . . . . 20 lines MAP_ZONE . . . . . . . . . . . . . . . . . . . . . 10 lines MATCH_ZONE . . . . . . . . . . . . . . . . . . . . 10 lines OUT_ZONE . . . . . . . . . . . . . . . . . . . . . 10 lines TYPEPACK . . . . . . . . . . 3 definition lines per PACKER MAXDUPES . . . . . . . . . . . . . . . . . . . . . no limit WILDMAIL! v2.09 Page 39 APPENDIX B TOSSING MAIL IN DATE/TIME ORDER Mail bundles are tossed in date/time order, no matter what order they are received in, beginning with .SU0, .MO0, etc. .PKT files are tossed in date/time order also. NODE NUMBER SYNTAX SHORTCUTS WM supports some shortcuts in the specification of Zone, Net, and Node numbers. The first shortcut is the assumed Zone or Net number. These lines are all equivalent: 1:161/502 1:106/123 1:204/1 1:161/502 161/123 204/1 (Zone 1 is defaulted) 1:161/502 123 204/1 (Zone 1 and net 161 are defaulted) LARGE MESSAGES Messages that exceed the maximum line limit defined in MAKEWILD for it's respective conference are automatically split into smaller ones in order to maintain the integrity of the original message. In other words, if the incoming message contains 250 lines and the destination conference is set to 150, the first 146 lines are added to the initial message in WC along with a 4 line prompt indicating the split. WM then creates a new message using the same TO:, FROM: and SUBJECT: information and inserts a 4 line prompt (indicating the message continuation) and then adds the remaining 104 lines. WM will automatically add as many new messages as required to toss the original message into the WC conference. NO CONTENT MESSAGES A NO CONTENT message (null message) is defined as any message not having any text body. WILDMAIL! v2.09 Page 40 FRONTDOOR BATCH FILES This section is offered as a reference when using WILDMAIL! with the front end mailer called FrontDoor. This is a very popular mailer and can be downloaded from just about any BBS under the name of FD202.ARJ. The current version as of this writing is v2.02. This section is devoted to the associated batch files and NOT the actual setup of FrontDoor via the FDSETUP program. For specific information on FDSETUP, refer to its author for technical support. Again, the information presented here is for reference only! We can not offer support on FrontDoor, but we have included this section due to it's popularity. ASSOCIATED BATCH FILES FrontDoor can be run standalone, but for use with WILDMAIL! it MUST be run from a batch file. This file for our example purposes will be called CAT.BAT. When using FrontDoor/WILDMAIL!/WILDCAT!, there are three batch files involved in this process. These files all exist in the \FD directory. Shown below is a brief description of these files. CAT.BAT - This is the main batch file used when running FrontDoor. After this file has been executed, FrontDoor will be ready to receive calls and if a human caller is detected, it will then pass control to DOBBS.BAT via the DOS CALL command. DOBBS.BAT - When a human caller is detected, FrontDoor will create this file in the \FD directory overwriting the previous DOBBS.BAT file and exit with a errorlevel 100. This is a one line batch file that executes EXEBBS.BAT and contains information that will be passed to WILDCAT! for proper operation. EXEBBS.BAT - This is the main batch file used to execute WILDCAT! This file will test the contents of DOBBS.BAT for specific character strings for use in determining whether or not this is a reliable connection. This information is then passed onto WILDCAT! to enable/disable the error correcting type protocols. WILDMAIL! v2.09 Page 41 FRONTDOOR BATCH FILES SYSTEM FLOW The basic flow of these batch files when a human caller connects to FrontDoor is as follows. CAT.BAT -> DOBBS.BAT -> EXEBBS.BAT (then return to CAT.BAT). When CAT.BAT is executed, FrontDoor will be brought up and will be waiting for calls. When a human caller connects and FrontDoor displays the "Press Escape twice for WILDCAT!" message and after pressing escape twice, FrontDoor will drop with a errorlevel 100 and create a batch file called DOBBS.BAT in the \FD directory. This batch file contains information on the connect speed, com port, time remaining until FrontDoor's next event and a possible reliable connect mode string if the modem returned one. In the CAT.BAT file, after dropping with a errorlevel 100, the batch file will instruct it to use the CALL command when executing DOBBS.BAT. This will ensure that when DOBBS.BAT is finished executing, it will return program execution to CAT.BAT. DOBBS.BAT then executes a batch file called EXEBBS.BAT which in turn tests for various reliable connect strings and then executes the appropriate command line to bring up WILDCAT! When the caller logs off the BBS, WILDCAT! will terminate and program flow will return to EXEBBS.BAT. This file basically just "ends" and returns to the batch file that executed it called DOBBS.BAT and since there was only one line to that batch file, it will then return to the CAT.BAT file and continue to the NEXT line AFTER executing the CALL command and continue on. The program flow will return to the main loop and bring FrontDoor back up waiting for calls. If a mail call happens, the basic flow will remain in CAT.BAT and execute WILDMAIL! for processing and then return to FrontDoor. For additional information on this process, refer to the section regarding the CAT.BAT file. This may sound a little complicated, but in the following examples, we will try and make more sense out of this. WILDMAIL! v2.09 Page 42 CAT.BAT FILE Below is a sample batch file used to run FrontDoor as a front end mailer for WILDCAT! v3.x. Throughout the example batch files, line numbers are shown to the immediate left with the > symbols. ie. 23> refers to line 23. They DO NOT EXIST in the actual batch file. 1> @echo off 2> cls 3> SET FD=c:\fd 4> SET WCNODEID=1 5> SET WCMDM=USRHST 6> :START 7> c: 8> cd\fd 9> fd -NOUNPACK 10> IF ERRORLEVEL 100 goto RUN-BBS 11> IF ERRORLEVEL 90 goto SCAN-TOSS 12> IF ERRORLEVEL 80 goto LOCAL-BBS 13> IF ERRORLEVEL 1 goto EXIT 14> IF ERRORLEVEL 0 goto EXIT 15> goto START 16> :RUN-BBS 17> call DOBBS.BAT 18> goto START 19> :SCAN-TOSS 20> cls 21> c: 22> cd\wildmail 23> wm toss scan 24> goto START 25> :LOCAL-BBS 26> c: 27> cd\wc30 28> wildcat /B LOCAL 29> goto START 30> :EXIT The following descriptions of this batch files assumes some understanding of how to create and use batch files. The batch files used in these examples make use of 2 important DOS commands, the IF ERRORLEVEL/GOTO and the LABEL commands. Please refer to the appropriate DOS manual for specifics if necessary. WILDMAIL! v2.09 Page 43 CAT.BAT FILE CAT.BAT FILE EXPLANATION Line #1 - Simply turns off all display for each command that's executed from this file. Line #2 - This clears the screen. Line #3 - Sets environment variable FD equal to the path where all the FrontDoor system files are located and is required by FrontDoor. Line #4 - Lines #4 and #5 are used for WILDCAT! to set the Node ID and the appropriate modem definition file (.MDM) to use for operation when WILDCAT! is executed. Line #6 - This is the MAIN PROGRAM LOOP label. Line #7 - Changes to the appropriate drive letter. You will need to specify here which one is required for your system. Line #8 - Change directories to the location of the FrontDoor program files. Line #9 - This line actually executes FrontDoor. Notice the command line parameter, -NOUNPACK. This command is used to make sure netmail messages are properly tossed into WILDCAT! If this parameter is NOT used, FrontDoor will grab these messages and toss it into it's own internal message base and delete them before WILDMAIL! can properly process them. Line 10 - This line tests to see of the errorlevel returned by FrontDoor when it exited equals the value of 100. If it does, then it will 'goto' the label called RUN-BBS in line #16. This will start the process of bringing up the BBS. This is desired when a caller connects and presses the Escape key twice. Line 11 - This functions exactly the same was as line #10 does, except it will 'goto' a label called SCAN-TOSS on line #19. This is used with the active events 'behavior' option when preparing to process the incoming mail. Normally, after mail has been received, FrontDoor will drop with this errorlevel (any number can be specified, but must be defined in FDSETUP) and then jump to line #19 to start execution of WILDMAIL! WILDMAIL! v2.09 Page 44 CAT.BAT FILE Line 12 - Same as line #10 except tests for an errorlevel of 80 and if so, jumps to the label called LOCAL-BBS on line #25. This is a user defined errorlevel used to bring up the BBS in local mode. This value is defined in FDSETUP, under Mailer, Function Keys and is normally the F1 key to remain consistent with WILDCAT!'s SysOp logon. This option is presented here as a convenience and is not required for proper operation. Line 13 - Lines #13 and #14 are used to test for abnormal/normal shutting down (Alt-Q) of FrontDoor. These lines will jump to the label called EXIT on line #30 and will return you to the DOS prompt. This is a normal exit routine. Line 15 - This line is a simple safety valve used to restart FrontDoor in case one of the errorlevels didn't match the ones that were included here. Typically, this is some sort of abnormal exit from FrontDoor, and instead of ending up at the DOS prompt, this will attempt to restart FrontDoor. Line 16 - Lines #16, #17 and #18 are used when a human caller is detected and will used to bring up the BBS. This line contains the label for the MAIN LOOP when FrontDoor drops with an errorlevel 100 from line #10. Line 17 - This line executes the DOBBS.BAT batch file created when FrontDoor exited with a errorlevel 100. The CALL command is used here to ensure that when DOBBS.BAT is finished executing, it will RETURN TO LINE #18 of this file. Without the CALL command, when DOBBS.BAT was finished executing, it would simply drop to the DOS prompt. NOT GOOD! Line 18 - After DOBBS.BAT is finished executing, it will return to this line and then 'goto' the label called START on line #6. This will complete the process of the caller logging off the BBS and preparing to restart FrontDoor and be ready to take additional calls. Line 19 - This is the main WILDMAIL! program loop for processing mail. Line 20 - Clears the screen. WILDMAIL! v2.09 Page 45 CAT.BAT FILE Line 21 - Changes to the drive where the WILDMAIL! subdirectory is located. Line 22 - Changes to the WILDMAIL! subdirectory where all the configuration and executable files are located. Line 23 - Executes WILDMAIL! with the TOSS SCAN command line parameters. This will start the actual processing of mail. Line 24 - This terminates the mail processing loop and restarts FrontDoor by jumping to a label called START in line #6. Line 25 - The is the main LOCAL LOGON loop's label. This 'subroutine' is executed when FrontDoor drops with a errorlevel 80 from line #12. This is used to allow local logons to the BBS when the appropriate function key has been pressed while FrontDoor is up and waiting for calls. Line 26 - Changes to the drive where WILDCAT! is located. Line 27 - Changes to the subdirectory containing all the WILDCAT! files. Line 28 - Executes WILDCAT! using the options set in line #4 with the /B LOCAL command parameters for allowing local logons. Line 29 - After normal logoff, FrontDoor is brought back up by returning to line #6. Line 30 - This is the label used when FrontDoor is brought down via lines #13 or #14. This is the last line in the batch file and thus will return you to the DOS prompt. WILDMAIL! v2.09 Page 46 DOBBS.BAT FILE DOBBS.BAT FrontDoor MUST BE configured to drop with a errorlevel 100 on ALL POSSIBLE CONNECT SPEEDS and create the .BAT file. This information is found in FDSETUP under Mailer, Errorlevels. This is a one line batch file created by FrontDoor and will change from caller to caller. Shown below is a sample of this file. EXEBBS 9600 1 897 /ARQ/V32/LAPM/V42BIS ^^^^^^ ^^^^ ^ ^^^ ^^^^^^^^^^^^^^^^^^^^ %0 %1 %2 %3 %4 <----- DOS Variables Below is a breakdown of the above command line. %0 = Command that DOS will execute %1 = Connect speed determined by FrontDoor %2 = Communications port %3 = Minutes remaining until next event %4 = Reliable mode connect string (if applicable) This line will execute a file called EXEBBS.BAT in the \FD directory passing the speed as 9600 (%1), com port 1 (%2), 897 minutes (%3) until the next FrontDoor event and the connect string of /ARQ/V32/LAPM/V42BIS (%4). The contents of EXEBBS.BAT will then take this information and properly evaluate it and then execute it for proper operation in WILDCAT! WILDMAIL! v2.09 Page 47 EXEBBS.BAT FILE EXEBBS.BAT This batch file is used primarily to bring up WILDCAT! with the parameters passed from the calling batch file called DOBBS.BAT. The information contained in DOBBS.BAT is used to 'set up' WILDCAT! for the proper speed, time remaining before any FrontDoor events and whether or not this is a reliable connection. Sample EXEBBS.BAT file for use with FrontDoor. 1> @echo off 2> cls 3> SET comspec=c:\command.com 4> SET connect= 5> if %4 == /ARQ SET connect=/MNP 6> if %4 == /ARQ/HST SET connect=/MNP 7> if %4 == /ARQ/V32 SET connect=/MNP 8> if %4 == /ARQ/LAPM SET connect=/MNP 9> if %4 == /ARQ/MNP SET connect=/MNP 10> if %4 == /ARQ/HST/HST SET connect=/MNP 11> if %4 == /ARQ/LAPM/V42BIS SET connect=/MNP 12> if %4 == /ARQ/MNP/MNP5 SET connect=/MNP 13> if %4 == /ARQ/HST/HST/MNP5 SET connect=/MNP 14> if %4 == /ARQ/HST/HST/V42BIS SET connect=/MNP 15> if %4 == /ARQ/V32/LAPM/V42BIS SET connect=/MNP 16> if %4 == /ARQ/V32/MNP SET connect=/MNP 17> if %4 == /ARQ/V32/LAPM/MNP/MNP5 SET connect=/MNP 18> :START 19> c: 20> cd\wc30 21> ctty con 22> wildcat /B %1%connect% %3 WILDMAIL! v2.09 Page 48 EXEBBS.BAT FILE EXEBBS.BAT FILE EXPLANATION Line #1 - Simply turns off all display for each command that's executed from this file. Line #2 - This clears the screen. Line #3 - This is safety measure to make sure DOS knows where to look for COMMAND.COM. Line #4 - This is a very important DOS environment variable. This is used to pass the /MNP flag associated with the current connection to WILDCAT! to indicate whether or not this is a reliable connect. If this flag is set, WILDCAT! will make the Ymodem/G and 1K-Xmodem/G protocols available to the caller. For now, we are turning the flag off (actually removing the variable entirely) because we will test the connect string for a reliable connect in lines #5 thru #17. Line #5 - Lines #5 thru #17 are used to test the connect string information passed to us from the DOBBS.BAT file. If you refer to the section on the DOBBS.BAT file, note that this is DOS environment variable %4. Here we test for a exact match of the string supplied, if there is a match, we will turn on the flag used in line #4 (connect=) via the SET command, to now equal /MNP. If no match is found, the environment variable 'connect' will be untouched. The strings in these lines are ones outputted by your modem. You will need to review each possible combination for your EXACT modem type. The ones shown here are for the older USR Dual Standards without v.32bis. The strings you enter must be the ones that are a EXACT MATCH and indicate a reliable connect. Some modems use a simple /REL and others may be more complex. Line 18 - The MAIN PROGRAM LOOP for bringing up WILDCAT! Line 19 - Changes to the drive where WILDCAT! is located. Line 20 - Changes to the subdirectory containing all the WILDCAT! files. WILDMAIL! v2.09 Page 49 EXEBBS.BAT FILE Line 21 - Redirects output to the CONsole. This is a safety valve to make sure there are not conflicts as to where data is to be outputted to. This line is not normally needed, but is here in case a DOOR program goes nuts on you. Line 22 - This is the main command line that executes WILDCAT! The /B parameter is required and indicates that a front end mailer is used with this configuration and to look for additional command line information that is passed. If you recall in the DOBBS.BAT file, the DOS environment variable %1 indicated connect speed. The '%connect%' parameter is the reliable connect flag used in lines #4 thru #17 and %3 is the time remaining until the next FrontDoor event. To help understand this, we will use the contents of the example DOBBS.BAT file The command on line #22; wildcat /B %1%connect% %3 will be replaced with the parameters passed in DOBBS.BAT and will now look like: wildcat /B 9600/MNP 897 This indicates a reliable connection at 9600 baud with 897 minutes left until the next FrontDoor event. A match was found on line #15 so the DOS environment variable 'connect' now equals /MNP. If there wasn't a match in lines #5 thru #17, the command line would read: wildcat /B 9600 897 You will notice the /MNP parameter is now missing and WILDCAT! will not allow the Ymodem/G and 1K-Xmodem/G protocols. When the caller logs off the BBS, either normally, or by dropping carrier, WILDCAT! will exit and return to the EXEBBS.BAT file. Since there are no remaining lines in this batch file to execute, the program flow will return to DOBBS.BAT, and since there are no more lines to execute in the DOBBS.BAT file, it will return to the CAT.BAT file, line #18. This will then 'goto' line #6 and restart FrontDoor completing our 'human caller loop'.